Methods and apparatus for scheduling of services in a traffic-engineering network

ABSTRACT

Apparatus and methods are provided for scheduling services in a traffic-engineered communications network. In one aspect a method comprises: receiving a request to schedule a second service utilizing the network in a second time period, wherein the second time period overlaps a first time period in which a first service utilizing the network has already been scheduled; and computing a path for the second service through the network. The step of computing the path for the second service through the network comprises: responsive to a determination that the request is received less than the threshold period of time before the start of the first time period, disallowing the second service from pre-empting the first service.

TECHNICAL FIELD

Examples of the present disclosure relate to methods, apparatus andcomputer-readable media for scheduling of services in atraffic-engineered network.

BACKGROUND

In computer and telecommunication networks, a Path Computation Element(PCE) is the entity responsible for finding a suitable path in thenetwork between a source node and a destination node. The pathcomputation may be subject to one or more constraints for the pathitself and/or the network as a whole (e.g. to optimize one or moreperformance parameters).

One recent application of the PCE is in the Abstraction and Control ofTraffic-Engineered Networks (ACTN) networking paradigm, conceived tofacilitate virtual network operation and the creation of a virtualizedenvironment in which operators can view and control multi-subnet andmulti-technology networks as a single virtualized network.

Traffic engineering is a process by which the performance of a network,such as a telecommunications network, is evaluated and optimized.Traffic-oriented performance parameters may include one or more ofpacket delay, packet delay variation, packet loss and throughput.Traffic engineering may seek to optimize one or more of these parameters(either locally or globally), and one of the functions by which suchoptimization may be achieved is the routing function, to steer trafficthrough the network in the most effective way. Thus PCEs play animportant role in the efficient utilization of resources intraffic-engineered networks.

One known method of assigning resources to a particular session in atraffic-engineered network is the use of priorities. For example, eachsession or service may be assigned a “setup” priority and a “hold”priority. The setup priority is used in deciding whether the particularsession can pre-empt another session, while the hold priority is used indeciding whether a particular session can be pre-empted by anothersession. In this context, when an established session is “pre-empted”,the session is torn down or otherwise halted in favour of anothersession which utilizes some or all of the network resources which havebecome available as a consequence. A proposed session with a setuppriority which is higher than the hold priority of an existing sessionmay pre-empt that existing session. Therefore the priority values can beused to map the relative importance of sessions and co-ordinate thenetwork accordingly. More important sessions are more likely to beestablished and more likely to be maintained than less importantsessions.

Previous traffic-engineering solutions have operated in real time, withrequests to establish new services and sessions being actionedimmediately by the system. Thus a session may be set up (or not)immediately upon request, based on the priorities associated with therequested session and existing sessions, and the available resources inthe network. Similarly, an existing session is liable to be halted atany time if a request is received to establish a higher-priority sessionand there are insufficient available resources to meet that requestwithout pre-emption.

A recent improvement to traffic-engineered networking is theintroduction of time scheduling to reserve connectivity resources atfuture times. By this mechanism, users can reserve future resources fora service corresponding to a path between a source node and adestination node. Priority values may be used in a similar way for thesetime-scheduled sessions, allowing less-important sessions to bepre-empted by more-important sessions. However, allowing the arbitrarypre-emption of time-scheduled paths can make the computation of pathseven more complex. It is therefore desirable to mitigate the complexityof the path computation problem, particularly when that problem spansspatial dimensions (including multiple domains and technology layers)and the temporal dimension.

SUMMARY

One aspect of the disclosure provides a method in a path computationelement for a traffic-engineered telecommunications network. The methodcomprises: receiving a request to schedule a second service utilizingthe network in a second time period, wherein the second time periodoverlaps a first time period in which a first service utilizing thenetwork has already been scheduled; and computing a path for the secondservice through the network. The step of computing the path for thesecond service through the network comprises: responsive to adetermination that the request is received less than the thresholdperiod of time before the start of the first time period, disallowingthe second service from pre-empting the first service.

Another aspect provides a method in a path computation element for atraffic-engineered telecommunications network, The method comprises:during a first time period in which a first service is active on thenetwork, receiving a request to schedule a second service utilizing thenetwork in a second time period, wherein the second time period overlapsthe first time period; and computing a path for the second servicethrough the network. The step of computing the path for the secondservice through the network comprises, if the start of the second timeperiod is less than the threshold period of time after the request wasreceived, disallowing the second service from pre-empting the firstservice.

A further aspect provides a computer program comprising instructionswhich, when executed on at least one processor, cause the at least oneprocessor to carry out a method as recited above.

A yet further aspect of the disclosure provides an apparatus for atraffic-engineered telecommunications network. The apparatus comprises apath computation element configured to: receive a request to schedule asecond service utilizing the network in a second time period, whereinthe second time period overlaps a first time period in which a firstservice utilizing the network has already been scheduled; and compute apath for the second service through the network. The path computationelement is configured to compute the path for the second service throughthe network by, responsive to a determination that the request isreceived less than the threshold period of time before the start of thefirst time period, disallowing the second service from pre-empting thefirst service.

Another aspect provides an apparatus for a traffic-engineeredtelecommunications network. The apparatus comprises a path computationelement configured to: during a first time period in which a firstservice is active on the network, receive a request to schedule a secondservice utilizing the network in a second time period, wherein thesecond time period overlaps the first time period; and compute a pathfor the second service through the network. The path computation elementis configured to compute the path for the second service through thenetwork by, if the start of the second time period is less than thethreshold period of time after the request was received, disallowing thesecond service from pre-empting the first service.

A further aspect of the disclosure provides an apparatus for atraffic-engineered telecommunications network. The apparatus comprisinga processor and a memory. The memory contains instructions executable bythe processor such that the apparatus is operable to: receive a requestto schedule a second service utilizing the network in a second timeperiod, wherein the second time period overlaps a first time period inwhich a first service utilizing the network has already been scheduled;and compute a path for the second service through the network. Theapparatus is operable to compute the path for the second service throughthe network by, responsive to a determination that the request isreceived less than the threshold period of time before the start of thefirst time period, disallowing the second service from pre-empting thefirst service.

Another aspect provides an apparatus for a traffic-engineeredtelecommunications network. The apparatus comprises a processor and amemory. The memory contains instructions executable by the processorsuch that the apparatus is operable to: during a first time period inwhich a first service is active on the network, receive a request toschedule a second service utilizing the network in a second time period,wherein the second time period overlaps the first time period; andcompute a path for the second service through the network. The apparatusis operable to compute the path for the second service through thenetwork by, if the start of the second time period is less than thethreshold period of time after the request was received, disallowing thesecond service from pre-empting the first service.

A further aspect provides an apparatus for a traffic-engineeredtelecommunications network. The apparatus comprises: a receiving moduleconfigured to receive a request to schedule a second service utilizingthe network in a second time period, wherein the second time periodoverlaps a first time period in which a first service utilizing thenetwork has already been scheduled; and a path computation moduleconfigured to compute a path for the second service through the network.The path computation module is operable to compute the path for thesecond service through the network by, responsive to a determinationthat the request is received less than the threshold period of timebefore the start of the first time period, disallowing the secondservice from pre-empting the first service.

A yet further aspect of the disclosure provides an apparatus for atraffic-engineered telecommunications network. The apparatus comprises:a receiving module configured to, during a first time period in which afirst service is active on the network, receive a request to schedule asecond service utilizing the network in a second time period, whereinthe second time period overlaps the first time period; and a pathcomputation module configured to compute a path for the second servicethrough the network. The path computation module is configured tocompute the path for the second service through the network by, if thestart of the second time period is less than the threshold period oftime after the request was received, disallowing the second service frompre-empting the first service.

BRIEF DESCRIPTION OF THE DRAWINGS

For a better understanding of examples of the present disclosure, and toshow more clearly how the examples may be carried into effect, referencewill now be made, by way of example only, to the following drawings inwhich:

FIG. 1 is a schematic illustration of a network according to embodimentsof the disclosure;

FIG. 2 is a timeline illustrating scheduling of services according toembodiments of the disclosure;

FIG. 3 is a timeline illustrating scheduling of services according tofurther embodiments of the disclosure;

FIG. 4 is a flow chart of a method according to embodiments of thedisclosure;

FIG. 5 is a flow chart of a method according to further embodiments ofthe disclosure;

FIG. 6 is a schematic diagram of a network node according to embodimentsof the disclosure; and

FIG. 7 is a schematic diagram of a network node according to furtherembodiments of the disclosure.

DETAILED DESCRIPTION

The following sets forth specific details, such as particularembodiments or examples for purposes of explanation and not limitation.It will be appreciated by one skilled in the art that other examples maybe employed apart from these specific details. In some instances,detailed descriptions of well-known methods, nodes, interfaces,circuits, and devices are omitted so as not obscure the description withunnecessary detail. Those skilled in the art will appreciate that thefunctions described may be implemented in one or more nodes usinghardware circuitry (e.g., analog and/or discrete logic gatesinterconnected to perform a specialized function, ASICs, PLAs, etc.)and/or using software programs and data in conjunction with one or moredigital microprocessors or general purpose computers. Nodes thatcommunicate using the air interface also have suitable radiocommunications circuitry. Moreover, where appropriate the technology canadditionally be considered to be embodied entirely within any form ofcomputer-readable memory, such as solid-state memory, magnetic disk, oroptical disk containing an appropriate set of computer instructions thatwould cause a processor to carry out the techniques described herein.

Hardware implementation may include or encompass, without limitation,digital signal processor (DSP) hardware, a reduced instruction setprocessor, hardware (e.g., digital or analogue) circuitry including butnot limited to application specific integrated circuit(s) (ASIC) and/orfield programmable gate array(s) (FPGA(s)), and (where appropriate)state machines capable of performing such functions.

FIG. 1 shows a network 102 according to embodiments of the disclosure,and particularly the components concerned with the control of thenetwork 102. In the illustrated embodiment, the components are arrangedaccording to the ACTN paradigm, and ACTN terminology is used throughoutthe description of FIG. 1 and in other parts of the description. Thoseskilled in the art will appreciate that the concepts methods andapparatus described herein are equally applicable to other networkingparadigms, and may be adapted straightforwardly for use in thosenetworking paradigms. The embodiments disclosed herein are not limitedto ACTN.

The network 102 comprises a plurality of domains 104 a, 104 b, 104 c(collectively, 104), each managed by respective physical networkcontrollers (PNCs) 106 a, 106 b, 106 c (collectively, 106). The PNCseach communicate with a parent controller, which in the illustratedembodiment is termed a multi-domain service coordinator (MDSC) 108, andthe MDSC 108 communicates with one or more clients via one or morecustomer network controllers (CNCs) 110 (although only a single CNC isshown in FIG. 1). First and second network nodes or path elements (PEs)112 a, 112 b are coupled to domain 104 a, while a third network node orPE 112 c is coupled to domain 104 c.

Each PNC 106 is responsible for the configuration of network elementswithin its respective domain 104, monitoring the physical topology ofthe domain 104, and communicating that topology to the MDSC 108. Thephysical topology may be communicated to the MDSC in raw (i.e.unprocessed) or abstracted (i.e. processed) formats. The PNCs 106communicate with their respective domains 104 via respective southboundinterfaces (SBIs), and with the MDSC 108 via respective MDSC-PNCinterfaces (MPIs). In one embodiment, the messages communicated via theMPIs may be defined in terms of Yang and transported via the networkconfiguration protocol. In other embodiments, different protocols may beemployed. Each PNC 106 may also comprise a path computation element(PCE) responsible for the computation of paths between network nodes orpath elements (PEs) in their domain, i.e. intra-domain paths. Forexample, PNC 106 a may be responsible for computing a path between PE112 a and PE 112 b.

The MDSC 108 receives topological information from each of the PNCs 106,and thus is able to build a single end-to-end network topology coveringthe entire network 102. The end-to-end network topology may beabstracted (i.e. processed) so as to provide a consistent overview ofthe network regardless of different technologies and protocolsimplemented in each of the domains 104. The MDSC 108 may communicatethat harmonized view of the network to one or more CNCs via respectiveCNC-MDSC interfaces (CMIs). In one embodiment, the messages communicatedvia the CMIs may be defined in terms of Yang and transported via thenetwork configuration protocol. In other embodiments, differentprotocols may be employed. The MDSC 108 may also receive requests fromthe CNCs 110 via the CMIs for the creation of new connections, themodification of existing connections or scheduled connections, or theremoval of existing or scheduled connections.

The MDSC 108 thus enables management of the network 102 as a whole,allowing the maintenance of end-to-end services across multiple domains,the definition of virtual networks or slices across multiple domains,and additional services. The MDSC 108 may therefore comprise a PCEresponsible for the computation of paths between network nodes or PEs indifferent domains, i.e. inter-domain paths. For example, the MDSC 108may compute a path between PE 112 a or PE 112 b, and PE 112 c.

Instances of PCEs can therefore be found in the PNCs as well as theMDSC. Embodiments of the disclosure therefore relate to PNCs, MDSCs, andany network element or node in which a path computation element may befound.

Embodiments of the disclosure relate to the application of first and/orsecond thresholds to determine whether a scheduled or establishedservice may be pre-empted by another service that is to be scheduled.The first and second thresholds may be applied in addition to priorityvalues, such as the setup and hold priority values discussed above.

For example, in one embodiment, a second service may be allowed topre-empt a first service which is already scheduled, if the request toschedule the second service is received more than a first thresholdperiod of time before the start of the first time period. If the requestto schedule the second service is received less than the first thresholdperiod of time before the start of the first time period, the secondservice is not allowed to pre-empt the first service.

In another embodiment, a request to schedule a second service may bereceived while a first service is already active. The second service maybe allowed to pre-empt the first service if the requested start of thesecond service occurs at a time which is more than a second thresholdperiod of time after the request to schedule the second service isreceived. If the requested start of the second service occurs at a timewhich is less than the second threshold period of time after the requestis received, pre-emption of the first service by the second service maybe denied.

The first and second thresholds may be implemented together orseparately, and therefore embodiments of the disclosure include methodsand apparatus in which the first threshold is applied alone, methods andapparatus in which the second threshold is applied alone, and methodsand apparatus in which both the first and second thresholds are applied.

The computation of an appropriate path for a requested service can becomplex, and in general will take into account multiple factors, as wellas one or more of the thresholds discussed above. In some embodiments,the services may also be associated with priority values such as thesetup and hold priorities discussed above. For example, if a requestedsecond service has a lower priority than a first service which isalready scheduled or already active, the existing priority algorithm mayprevent pre-emption of the first service by the second service,regardless of the first and second thresholds discussed above.Conversely, if the second service has a higher priority than the firstservice, then one or both of the first and second thresholds may preventpre-emption of the first service regardless of that higher priority.

Therefore the application of the first and/or second thresholds may takeplace as part of a wider path computation process, in which additionalfactors are taken into account such as one or more priority valuesassociated with the first and second services; the source anddestination nodes of the first and second services; available resourcesin the network, etc.

FIG. 2 is a timeline showing application of the first thresholddiscussed above.

At time to, a first service (“Service 1” in the Figure) is scheduled fora time period between future times t₃ and t₄. Thus service 1 isscheduled to be active (i.e. implemented and available to consumers) inthe network in a first period of time, between times t₃ and t₄. This isshown by a solid line extending between times t₃ and t₄ in FIG. 2.

A request to schedule service 1 may have been received over the CMIinterface, and define or request one or more parameters for the service,such as the start and end times for the service (t₃ and t₄), the sourceand destination nodes for the service, and the available bandwidthrequested for the service. In some embodiments, service 1 may beindefinite, and therefore have no end time t₄. The request may alsodefine or request a quality of service (QoS) for the service.

According to embodiments of the disclosure, the QoS comprises a firstthreshold period of time associated with the service. The firstthreshold period of time (also referred to herein as “the firstthreshold”) extends before the scheduled start time t₃ of the service toan earlier time, t₂, and is illustrated by a dashed line in FIG. 2. Thefirst threshold may be defined in any suitable manner. For example, thefirst threshold may be defined by reference to the time t₂ itself, bythe length of the time period (t₃-t₂) or by some other parameter (e.g. amultiple of the period, t₄-t₃).

The QoS may also comprise one or more priority values associated withservice 1, such as a setup priority and/or a hold priority.

Service 1 is thus scheduled, and associated with a path through anetwork, such as network 102, as well as resources reserved to meet theQoS requirements of the service. The path is between a source (oringress) node and a destination (or egress) node, and may be intra- orinter-domain. The path may be a label-switched path (LSP), for example.

The path and associated parameters for the first service may be storedin the PCE responsible for computing the path (e.g. a PCE in the MDSC108 in the case of inter-domain paths, or a PCE in a PNC 106 in the caseof intra-domain paths). The path and associated parameters may also bepropagated to other PCEs to enable the computation of paths fordifferent services in future. For example, a PCE in a PNC 106 a mayforward to a PCE in the MDSC 108 the path and associated parameters foran intra-domain service in its respective domain 104 a. In this way, aPCE in the MDSC 108 is enabled to carry out inter-domain pathcomputation utilizing the resources of the domain 104 a. Further sharingof resource information may be carried out between PCEs within PNCs 106for different domains.

At time t₁, a request is received to schedule a second service (“Service2”) in a second period of time. The second period of time begins whilethe first service is scheduled to be active (i.e., between t₃ and t₄),and thus the second period of time partially overlaps the first periodof time. In other embodiments, the second period of time may beginbefore the start of the first period of time and end after the start ofthe first period of time, or may overlap the first period of timecompletely. In other words, service 2 is requested to be active in thenetwork at at least one time when service 1 is already scheduled to beactive.

As with service 1, the request to schedule service 2 may define orrequest one or more parameters for the service. The one or moreparameters may comprise one or more of: the start time for the service,the end time for the service, the source node for the service, thedestination node for the service, and the available bandwidth requestedfor the service. In some embodiments, service 2 may be indefinite, andtherefore have no end time. The request may also define or request aquality of service (QoS) for the service. The QoS may comprise arespective first threshold period of time for the service, and one ormore priority values, such as a setup priority value and/or a holdpriority value.

The PCE which receives the request to schedule the second service musttherefore compute a path for the second service based on the parameterscontained within the request. The computation of the path in general isa multi-factorial problem that takes into account multiple factors suchas the source and destination for the path, any priorities associatedwith requested, established and scheduled services, the availableresources in the network, etc.

According to embodiments of the disclosure, the first threshold periodof time is applied to determine whether or not service 2 is allowed topre-empt service 1. A new service, which is requested less than thefirst threshold period of time before the start of an already scheduledservice, may be prevented from pre-empting that already scheduledservice regardless of the relative priorities of the new and scheduledservices. If the new service is requested more than the first thresholdperiod of time before the start of the already scheduled service, thenthe new service is allowed to pre-empt the scheduled service. Thus theresources for the already scheduled service may be made available forthe calculation of a path for the new service. Whether the new serviceactually does pre-empt the already scheduled service may depend on anumber of further factors.

In the illustrated example, the request to schedule service 2 isreceived before t₂, i.e., more than the threshold period of time beforethe scheduled start time t₃ of service 1. Therefore service 2 is allowedto pre-empt service 1. If the request to schedule service 2 was receivedafter t₂, i.e., less than the threshold period of time before thescheduled start time t₃ of service 1, then service 2 would be preventedfrom pre-empting service 1.

For illustrative purposes, here we assume that service 2 has a higherpriority than service 1. For example, the setup priority for service 2may be higher than the hold priority of service 1. Thus, based on thatcriterion, service 2 is allowed to pre-empt service 1, i.e. to utilizesome or all of the resources reserved for service 1, and require thatservice 1 be de-scheduled. Thus the computation of a path for service 2may utilize the resources that have previously been scheduled forservice 1, i.e. service 2 is allowed to pre-empt service 1.

In some embodiments, the PCE may first attempt to compute a path forservice 2 in which no pre-emption is required. For example, the PCE mayattempt to compute a path for service 2 using only the resources thatare available (i.e. not scheduled for use by another service) in thenetwork. If no path is possible which meets the parameters requested forservice 2, using that method, the PCE may then go on to attempt tocompute a path for service 2 in which service 1 is pre-empted.

Thus FIG. 2 illustrates a method by which the computation of a path fora newly requested service may be limited to resources that are notpreviously scheduled for use by other services, provided that therequest to schedule the new service is received more than a thresholdperiod of time before those other services. The computation of a pathfor the new service is thus simplified.

FIG. 3 is a timeline showing application of the second thresholddiscussed above.

In this timeline, a first service (“service 1”) is already active withinthe network, i.e. the network has been appropriately configured toprovide resources for a path between a source node and a destinationnode. Service 1 may be associated with one or more parameters, such asone or more of: the path for service 1 (i.e. between a source node and adestination node), the resources being utilized by service 1 (e.g. thebandwidth), an end time of service 1 (unless the service is indefinite),and one or more priority values for service 1. For example, service 1may be associated with a setup priority and/or a hold priority. In thisexample, service 1 is scheduled to end at time t₃. The time during whichservice 1 is scheduled to be active is termed the first period of time.

According to embodiments of the disclosure, service 1 is also associatedwith a second threshold period of time (termed “second” to distinguishit from the first threshold period of time discussed above). The secondthreshold period of time defines a period of time following receipt of arequest to schedule a second service, after which the second service maypre-empt the first service.

At time to, a request is received at the PCE to schedule a secondservice (“service 2”) in a second period of time. The second period oftime begins at a time t₂ while the first service is scheduled to beactive (i.e., before t₃) and ends at a time to while the first serviceis not scheduled to be active (i.e., after t₃), and thus the secondperiod of time partially overlaps the first period of time. In otherembodiments, the second period of time may begin and end before the endof the first period of time and thus overlap the first period of timecompletely. In other words, service 2 is requested to be active in thenetwork at at least one time when service 1 is already scheduled to beactive.

As with service 1, the request to schedule service 2 may define orrequest one or more parameters for the service. The one or moreparameters may comprise one or more of: the start time for the service,the end time for the service, the source node for the service, thedestination node for the service, and the available bandwidth requestedfor the service. In some embodiments, service 2 may be indefinite, andtherefore have no end time. The request may also define or request aquality of service (QoS) for the service. The QoS may comprise arespective second threshold period of time for the service, and one ormore priority values, such as a setup priority value and/or a holdpriority value.

The PCE which receives the request to schedule the second service musttherefore compute a path for the second service based on the parameterscontained within the request. The computation of the path in general isa multi-factorial problem that takes into account multiple factors suchas the source and destination for the path, any priorities associatedwith requested, established and scheduled services, the availableresources in the network, etc.

According to embodiments of the disclosure, the second threshold periodof time is applied to determine whether or not service 2 is allowed topre-empt service 1. A new service, which is scheduled to begin less thanthe second threshold period of time after the request to schedule thenew service is received, may be prevented from pre-empting that alreadyactive service regardless of the relative priorities of the new andscheduled services. If the new service is requested to begin at a timewhich is more than the second threshold period of time after the requestis received, then the new service is allowed to pre-empt the activeservice. Thus the resources for the already active service may be madeavailable for the calculation of a path for the new service.

Whether the new service actually does pre-empt the active service maydepend on a number of further factors.

In the illustrated example, the second threshold period of time forservice 1 begins at time to (i.e. when the request to schedule service 2is received) and ends at time t₁. Service 2 is requested to begin attime t₂, which is after t₁, and therefore service 2 is allowed topre-empt service 1.

Whether service 2 actually does pre-empt service 1 may take into accounta number of other factors. For example, the PCE may first attempt tocompute a path for service 2 in which no pre-emption is required. Forexample, the PCE may attempt to compute a path for service 2 using onlythe resources that are available (i.e. not scheduled for use by anotherservice) in the network. If no path is possible which meets theparameters requested for service 2 using that method, the PCE may thengo on to attempt to compute a path for service 2 in which service 1 ispre-empted.

The PCE may also take into account priority values associated withservice 1 and service 2. If service 2 has a lower priority than service1, for example if the setup priority for service 2 is lower than thehold priority for service 1, then no pre-emption of service 1 by service2 may be permitted. Conversely, if the setup priority of service 2 ishigher than the hold priority of service 1, then pre-emption may bepermitted. In that case, service 2 is allowed to pre-empt service 1,i.e. to utilize some or all of the resources currently being utilized byservice 1, and require that service 1 be discontinued (e.g. torn down).Thus the computation of a path for service 2 may utilize the resourcesthat are currently reserved for use by service 1, i.e. service 2 isallowed to pre-empt service 1.

FIG. 4 is a flowchart of a method according to embodiments of thedisclosure, for computing a path for a requested service. The method maybe carried out in a PCE in a network node (such as a PNC 106 or MDSC108) for a network. The network node may be a physical node or a virtualnode (i.e. a virtual application running on a server).

In general, the network and the protocols implemented within it mayallow for services to be scheduled to begin at some time in the future.Thus one or more services may be active on the network (i.e. establishedand routing traffic along a defined path) and/or scheduled on thenetwork for the future. Each service which is active and/or scheduledmay be associated with one or more parameters, such as a path between asource node and a destination node (e.g. a label switched path);resources required to operate the service on the path (e.g. abandwidth); one or more priority values (e.g. such as a setup priorityand/or a hold priority); and one or more threshold values (e.g. such asthe first and second thresholds defined above). Each service (whetheractive or scheduled) and its associated parameters may be stored in thePCE which has responsibility for the domain or domains in which theservice is active or scheduled. For example, if the service isintra-domain, the service and its parameters may be stored in a PCEinstance running on a PNC associated with the domain, a PCE instancerunning on a MDSC which oversees the domain as well as other domains, orboth. If the service is inter-domain, the service and its parameters maybe stored in a PCE instance running on a MDSC which oversees the domainsthrough which the path is established.

In step 402, the PCE receives a request to schedule a new service(termed “service 2”). The request may be received from a CNC, andactioned within the MDSC, or passed to a PNC and actioned there. Therequest may define one or more parameters, such as: a source node and adestination node within the network; a required bandwidth; one or morepriority values (e.g. a setup priority and/or a hold priority); and oneor more threshold values (e.g. the first and/or second thresholdsdefined above).

In step 404, the PCE computes a path for the requested new service.Techniques for computing paths are well known to those skilled in theart and are not described in detail herein. In general, the problem is amulti-factorial one which requires the optimization of a solutionsubject to one or more constraints. For example, the constraints maycomprise one or more of: the source and destination nodes; the availableresources in the network.

In one embodiment, step 404 comprises the sub-step 406 of determiningfirst whether a path is possible for the new service in which noexisting or scheduled service is pre-empted. Thus, in this instance, thepath computation problem may consider as a constraint the networkresources which are not previously committed to an active service or ascheduled service at the times for which the new service is requested,i.e. the available resources. In such embodiments, the goal of the pathcomputation is to avoid pre-emption where possible, so as to avoiddisruption to existing and previously scheduled services (which wouldrequire new paths to be computed, etc). Therefore, if a path is possiblewithout pre-emption, the process moves to step 408, in which the newservice is scheduled with the non-pre-empting path. The PCE may alsostore the new service and its associated parameters, and/or forward suchinformation to the MDSC, to be used in the computation of paths forfuture services that may be requested.

If no path is possible for the new service without pre-empting one ormore existing or scheduled services, the method moves to step 410 inwhich the path computation algorithm is performed again, using resourcesthat are already in use by one or more existing services, or that arealready scheduled for use by one or more services. Thus themulti-factorial algorithm is repeated, but using the more relaxedconstraint in which the available resources include those resourcesallocated to existing or scheduled services which can be pre-empted.Further detail concerning whether resources for a particular service canbe utilized in this algorithm can be found below in the description ofFIG. 5.

Of course, it may be that no path is possible for the new requestedservice, even with the more relaxed constraints described above. In thatcase, communication may be required with the client for the new serviceto the effect that the requested service cannot be implemented withinthe network. The client may submit a new request in which priorityvalues are increased, to increase the likelihood that a path can befound for the new service, or find some alternative solution for theservice (such as an alternative network provider).

Here we assume that a suitable path can be found for the new requestedservice, using the more relaxed constraints afforded by pre-emption ofone or more existing or scheduled services. The process moves to step412, in which the clients for the pre-empted services are notified thattheir service (whether active or scheduled) has been pre-empted byanother service. For example, an automated message may be sent to theclient via a CNC. The client may then be able to seek an alternativesolution for their pre-empted service, such as an alternative networkprovider or network. The notification message may include an expectedstart time of the pre-empting service, or a time at which the existingservice is to be torn down.

In step 414, the pre-empting path is scheduled for the newly requestedservice. As in step 408, the PCE may also store the new service and itsassociated parameters, and/or forward such information to the MDSC, tobe used in the computation of paths for future services that may berequested.

FIG. 4 thus shows a method in which a path is computed for a newlyrequested service. In the illustrated embodiment, it is first determinedwhether a path is possible for the requested service that does notrequire pre-emption and, if so, this path is used in preference to otherpaths. However, in alternative embodiments different criteria may bespecified. For example, it may be found that an optimal path for the newservice, regardless of whether that path pre-empts one or more active orscheduled services, leads to optimal usage of the network. Thus the PCEmay compute a path for the requested service based on the availableresources including those available via pre-emption, without firstdetermining whether a path is possible without pre-emption.

FIG. 5 is a flowchart of a method according to embodiments of thedisclosure, for determining whether a requested service (service 2) isallowed to pre-empt another service (service x) which is active orscheduled in the network. The method may be carried out in a PCE in anetwork node (such as a PNC 106 or MDSC 108). The network node may be aphysical node or a virtual node (i.e. a virtual application running on aserver). The method may be carried out as a sub-step to step 410, inwhich a path is computed for a newly requested service using pre-emptionof one or more existing or scheduled services.

In step 502, the PCE determines whether service 2 is associated with ahigher priority than service x. For example, service 2 may be associatedwith a setup priority value, and service x may be associated with a holdpriority value. If service 2 does not have a higher priority thanservice x, the method proceeds to step 504 in which service 2 isprevented from pre-empting service x. That is, the resources being usedor reserved for use by service x are not made available for thecalculation of a path for service 2.

If it is determined that service 2 has a higher priority than service x,the process moves to step 506. Note that the case where service 2 hasthe same priority as service x has not been discussed here. Thiseventuality may be handled either by allowing pre-emption of service x(i.e. the method moving to step 506), or preventing it (i.e. moving tostep 504).

In step 506, the PCE determines whether the request to schedule service2 was received within a pre-emption threshold (i.e a first threshold)associated with service x. As noted in FIG. 2, the pre-emption thresholdextends before the scheduled start time of service x. If the request toschedule service 2 is received during that threshold period of time(e.g. but before service x is active), then pre-emption of service x isprevented and the process moves to step 504. That is, the resourcesreserved for use by service x are not made available for the calculationof a path for service 2.

If the request to schedule service 2 is received before that thresholdperiod of time, or if service x is already active, then the processmoves to step 508 in which the PCE determines whether the requestedstart time of service 2 is a notice threshold period of time (i.e. asecond threshold) after the request to schedule service 2 was received.As shown in FIG. 3, the notice period of time is associated with anexisting, active service, and provides a period of time in which thatexisting service may not be pre-empted by newly requested services. Ifit is determined that service 2 is requested to start at a time which isless than the notice threshold period of time after the request toschedule service 2 is received, then pre-emption of service x by service2 is prevented and the process moves to step 504. That is, the resourcesreserved for use by service x are not made available for the calculationof a path for service 2.

If it is determined that service 2 is requested to start at a time whichis later than the notice threshold period of time after the request toschedule service 2 is received, or if service x is not yet active in thenetwork, then pre-emption of service x by service 2 is allowed and theprocess moves to step 510. That is, the resources being used by servicex or reserved for use by service x are made available for thecalculation of a path for service 2.

Note that this process may be repeated for multiple or all servicesutilizing resources in the network, or multiple or all servicesutilizing resources which may be useful for the calculation of a pathfor service 2.

It will also be understood by those skilled in the art that the processshown in FIG. 5 may be carried out in any order. That is, steps 502, 506and 508 (analysing priority values, pre-emption threshold and noticethreshold respectively) may be carried out in any order. Further, steps506 and 508 may be carried out independently of each other in someembodiments. That is, it may be determined whether service x is activeor scheduled to be active. If it is determined that service x is active,only the notice threshold in step 508 may be applied. If it isdetermined that service x is scheduled but currently inactive, then onlythe pre-emption threshold in step 506 may be applied.

Thus FIGS. 4 and 5 describe a method by which a path may be computed fora newly requested service, and particularly define various parametersthat may be used to remove resources already in use or already scheduledfor use by other services from the path computation problem. Althoughthis may make it less likely that a path can be found for the newlyrequested service, the path computation problem is simplified, and lessdisruption may be caused to services which are already active or alreadyscheduled.

FIG. 6 is a schematic drawing of a network node 600 according toembodiments of the disclosure. For example, the network node 600 may bea PNC or a MDSC, and may be physical or virtual. The network node 600may be configured to perform the method of FIGS. 4 and 5.

The network node 600 comprises a processor 602 and a memory 604. Thememory 604 contains instructions executable by the processor 602.

In one embodiment, the apparatus 600 is operable to: receive a requestto schedule a second service utilizing the network in a second timeperiod, wherein the second time period overlaps a first time period inwhich a first service utilizing the network has already been scheduled;and compute a path for the second service through the network. Thenetwork node 600 may be operable to compute the path for the secondservice through the network by: responsive to a determination that therequest is received less than the threshold period of time before thestart of the first time period, disallowing the second service frompre-empting the first service.

In another embodiment, the apparatus 604 is operable to: during a firsttime period in which a first service is active on the network, receive arequest to schedule a second service utilizing the network in a secondtime period, wherein the second time period overlaps the first timeperiod; and compute a path for the second service through the network.The network node 600 may be operable to compute the path for the secondservice through the network by: if the start of the second time periodis less than the threshold period of time after the request wasreceived, disallowing the second service from pre-empting the firstservice.

The apparatus further comprises an interface, 606, for connecting to thenetwork and via said network to other elements of the network.

FIG. 7 is a schematic drawing of a network node 700 according to furtherembodiments of the disclosure. For example, the network node 700 may bea PNC or a MDSC, and may be physical or virtual. The network node 700may be configured to perform the method of FIGS. 4 and 5.

The network node 700 comprises a receiving module 702 and a pathcomputation module 704. The path computation module 704 may comprise apre-emption module 706 configured to determine whether a first serviceis allowed to pre-empt a second service or not.

In one embodiment, the receiving module 702 is configured to receive arequest to schedule a second service utilizing the network in a secondtime period, wherein the second time period overlaps a first time periodin which a first service utilizing the network has already beenscheduled. The path computation module 704 is configured to compute apath for the second service through the network. The path computationmodule 704 (or the pre-emption module 706) is configured to compute apath for the second service through the network by, responsive to adetermination that the request is received less than the thresholdperiod of time before the start of the first time period, disallowingthe second service from pre-empting the first service.

In another embodiment, the receiving module 702 is configured to, duringa first time period in which a first service is active on the network,receive a request to schedule a second service utilizing the network ina second time period, wherein the second time period overlaps the firsttime period. The path computation module 704 is configured to compute apath for the second service through the network. The path computationmodule (or the pre-emption module 706) is configured to compute the pathfor the second service through the network by, if the start of thesecond time period is less than the threshold period of time after therequest was received, disallowing the second service from pre-emptingthe first service.

The apparatus further comprises an interface, 708, for connecting to thenetwork and via said network to other elements of the network.

The present disclosure thus provides apparatus and methods forscheduling services in a traffic-engineered communications network.

It should be noted that the above-mentioned examples illustrate ratherthan limit the invention, and that those skilled in the art will be ableto design many alternative examples without departing from the scope ofthe appended statements. The word “comprising” does not exclude thepresence of elements or steps other than those listed in a claim, “a” or“an” does not exclude a plurality, and a single processor or other unitmay fulfil the functions of several units recited in the statementsbelow. Where the terms, “first”, “second” etc are used they are to beunderstood merely as labels for the convenient identification of aparticular feature. In particular, they are not to be interpreted asdescribing the first or the second feature of a plurality of suchfeatures (i.e. the first or second of such features to occur in time orspace) unless explicitly stated otherwise. Steps in the methodsdisclosed herein may be carried out in any order unless expresslyotherwise stated. Any reference signs in the statements shall not beconstrued so as to limit their scope.

1. A method in a path computation element for a traffic-engineeredtelecommunications network, the method comprising: receiving a requestto schedule a second service utilizing the network in a second timeperiod, wherein the second time period overlaps a first time period inwhich a first service utilizing the network has already been scheduled;and computing a path for the second service through the network, whereinthe step of computing the path for the second service through thenetwork comprises: responsive to a determination that the request isreceived less than the threshold period of time before the start of thefirst time period, disallowing the second service from pre-empting thefirst service.
 2. The method according to claim 1, wherein the step ofcomputing the path for the second service through the network furthercomprises: responsive to a determination that the request is receivedmore than a threshold period of time before the start of the first timeperiod, allowing the second service to pre-empt the first service. 3.The method according to claim 2, wherein the step of computing the pathfor the second service through the network further comprises: responsiveto a determination that the second service is associated with a higherpriority than the first service, allowing the second service to pre-emptthe first service; and responsive to a determination that the secondservice is associated with a lower priority than the first service,disallowing the second service from pre-empting the first service. 4.The method according to claim 1, wherein the threshold is associatedwith the first service.
 5. The method according to claim 4, wherein thethreshold is configured within a request to schedule the first servicein the first time period, received by the path computation element. 6.The method according to claim 1, wherein the step of computing a pathfor the second service comprises computing a path that pre-empts thefirst service, the method further comprising: notifying a client for thefirst service that the first service has been pre-empted.
 7. The methodaccording to claim 1, further comprising: during the first time periodin which the first service is active on the network, receiving a requestto schedule a third service utilizing the network in a third timeperiod, wherein the third time period overlaps the first time period;and computing a path for the third service through the network, whereinthe step of computing the path for the third service through the networkcomprises: responsive to a determination that the start of the thirdtime period is less than the second threshold period of time after therequest to schedule the third service was received, disallowing thethird service from pre-empting the first service. 8-11. (canceled)
 12. Amethod in a path computation element for a traffic-engineeredtelecommunications network, the method comprising: during a first timeperiod in which a first service is active on the network, receivingrequest to schedule a second service utilizing the network in a secondtime period, wherein the second time period overlaps the first timeperiod; and computing a path for the second service through the network,wherein the step of computing the path for the second service throughthe network comprises: responsive to a determination that the start ofthe second time period is less than the threshold period of time afterthe request was received, disallowing the second service frompre-empting the first service.
 13. The method according to claim 12,wherein the step of computing the path for the second service throughthe network further comprises: responsive to a determination that thestart of the second time period is greater than a threshold period oftime after the request was received, allowing the second service topre-empt the first service.
 14. The method according to claim 13,wherein the step of computing the path for the second service throughthe network further comprises: responsive to a determination that thesecond service is associated with a higher priority than the firstservice, allowing the second service to pre-empt the first service; andresponsive to a determination that the second service is associated witha lower priority than the first service, disallowing the second servicefrom pre-empting the first service.
 15. The method according to claim12, wherein the step of computing a path for the second servicecomprises computing a path that pre-empts the first service, the methodfurther comprising: notifying a client for the first service ofpre-emption of the first service.
 16. The method according to claim 15,further comprising: notifying the client for the first service of thetime at which the first service will end.
 17. The method according toclaim 12, wherein the threshold is associated with the first service.18. (canceled)
 19. The method according to claim 12, wherein the requestto schedule the second service comprises one or more constraints to bemet by the path through the network, and wherein the step of computingthe path for the second service comprises computing the path for thesecond service such that the one or more constraints are satisfied.20-27. (canceled)
 28. Apparatus for a traffic-engineeredtelecommunications network, the apparatus comprising a processor and amemory, the memory containing instructions executable by the processorsuch that the apparatus is operable to: receive a request to schedule asecond service utilizing the network in a second time period, whereinthe second time period overlaps a first time period in which a firstservice utilizing the network has already been scheduled; and compute apath for the second service through the network, wherein the apparatusis operable to compute the path for the second service through thenetwork by: responsive to a determination that the request is receivedless than the threshold period of time before the start of the firsttime period, disallowing the second service from pre-empting the firstservice.
 29. Apparatus according to claim 28, wherein the apparatus isoperable to compute the path for the second service by: responsive to adetermination that the request is received more than a threshold periodof time before the start of the first time period, allowing the secondservice to pre-empt the first service.
 30. Apparatus according to claim29, wherein the apparatus is operable to compute the path for the secondservice by: responsive to a determination that the second service isassociated with a higher priority than the first service, allowing thesecond service to pre-empt the first service; and responsive to adetermination that the second service is associated with a lowerpriority than the first service, disallowing the second service frompre-empting the first service.
 31. Apparatus according to claim 28,wherein the apparatus is operable to compute a path that pre-empts thefirst service, the apparatus being further operable to: notify a clientfor the first service that the first service has been pre-empted. 32.Apparatus according to claim 28, wherein the apparatus is furtheroperable to: during the first time period in which the first service isactive on the network, receive a request to schedule a third serviceutilizing the network in a third time period, wherein the third timeperiod overlaps the first time period; and compute a path for the thirdservice through the network, wherein the apparatus is operable tocompute the path for the third service by: responsive to a determinationthat the start of the third time period is less than the secondthreshold period of time after the request to schedule the third servicewas received, disallowing the third service from pre-empting the firstservice. 33-34. (canceled)
 35. Apparatus for a traffic-engineeredtelecommunications network, the apparatus comprising a processor and amemory, the memory containing instructions executable by the processorsuch that the apparatus is operable to: during a first time period inwhich a first service is active on the network, receive a request toschedule a second service utilizing the network in a second time period,wherein the second time period overlaps the first time period; andcompute a path for the second service through the network, wherein theapparatus is operable to compute the path for the second service throughthe network by: responsive to a determination that the start of thesecond time period is less than the threshold period of time after therequest was received, disallowing the second service from pre-emptingthe first service.
 36. Apparatus according to claim 35, wherein theapparatus is operable to compute the path for the second service by:responsive to a determination that the start of the second time periodis greater than a threshold period of time after the request wasreceived, allowing the second service to pre-empt the first service. 37.Apparatus according to claim 36, wherein the apparatus is operable tocompute the path for the second service by: responsive to adetermination that the second service is associated with a higherpriority than the first service, allowing the second service to pre-emptthe first service; and responsive to a determination that the secondservice is associated with a lower priority than the first service,disallowing the second service from pre-empting the first service. 38.Apparatus according to claim 35, wherein the apparatus is operable tocompute a path that pre-empts the first service, the apparatus beingfurther operable to: notify a client for the first service ofpre-emption of the first service.
 39. (canceled)
 40. Apparatus accordingto claim 28, wherein the path computation element is implemented withina multi-domain service coordinator or a physical network controller.41-42. (canceled)